Homeowners insurance application process using geotagged photos

ABSTRACT

Methods, systems, and computer readable media are disclosed for determining a homeowners insurance quote from a captured image of a dwelling. The captured image includes geotagged information, and the address of the dwelling is determined by reverse geocoding this information. An insurance premium quote may then be generated based on the reverse geocoded address and any additional risk assessment factors, such as the building characteristics. Verification of the address may also be performed by accessing one or more databases, which may store information including addresses, coordinates, and images associated with the address. The building characteristics may be retrieved from one or more of the databases to allow for quote generation with minimal user intervention. Matching properties having comparative quotes near the dwelling address may also be generated.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/259,676, which was filed on Apr. 23, 2014, the disclosure of which isincorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems, method, and apparatus forgenerating insurance premium quotes and, more particularly, to usinggeotagged location data in an image of a dwelling to generate insurancepremium quotes.

BACKGROUND

Homeowners insurance is practically a modern-day necessity. Often,people decide to voluntarily purchase homeowners insurance for their ownpeace of mind. Additionally, lenders and homeowners' associationstypically require a homeowner to maintain a homeowners insurance policy.Since owning a homeowners insurance policy is such common practice, thehomeowners insurance market has remained very competitive. As a result,homeowners often shop around for cheaper homeowners insurance premiums.Furthermore, homeowners may obtain several quotes for insurance premiumsprior to purchasing a home in an attempt to find a better rate.Homeowners insurance quotes may be obtained online, but it is oftendifficult or impractical to verify the information entered by a clientin such a manner.

Homeowners insurance premium quotes are based on several factorsincluding the building characteristics and location of the dwelling. Forexample, a frame house may demand a higher quoted premium than a brickhouse, since frame houses are typically more prone to fire damage.Furthermore, the location of a dwelling plays an important role indetermining risk assessment, since certain locations are more prone toloss than others. A person's unfamiliarity with building characteristicterminology may result in a cheaper (or more expensive) premium beingquoted. Additionally, entering an incorrect address directional (“S”instead of “N”) could severely impact the risk assessment factors and,in turn, the quoted premium. Therefore, ensuring the accuracy of onlinequoted homeowners insurance premiums presents several challenges.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a quoting system 10 in accordance with anexemplary embodiment of the present disclosure;

FIG. 2 illustrates a quote method 200 in accordance with an exemplaryembodiment of the present disclosure; and

FIG. 3 illustrates a quote method 300 in accordance with an exemplaryembodiment of the present disclosure.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of a quoting system 10 in accordance with anexemplary embodiment of the present disclosure. Quoting system 10includes a client device 14 configured to connect to a quoting engine 12via a network 16. Network 16 may include any appropriate combination ofwired and/or wireless communication networks. For example, network 16may include any combination of a local area network (LAN), ametropolitan area network (MAN), a wide area network (WAN), and mayfacilitate a connection to the Internet. To provide further examples,network 16 may include wired telephone and cable hardware, satellite,cellular phone communication networks, etc.

Client device 14 includes an image capture unit 42, a user interface 36,a central processing unit (CPU) 32, a graphics processing unit (GPU) 34,a memory 44, a display 38, a location acquisition unit 46, and acommunication unit 40. In an embodiment, client device 14 is implementedas a user equipment (UE), such as a mobile device, a computer, laptop,tablet, desktop, or any other suitable type of computing device.

Location acquisition unit 46 is configured to obtain location datacorresponding to a location of a device in which location acquisitionunit 46 is implemented, such as client device 14, for example. As willbe appreciated by those of skill in the relevant art(s), locationacquisition unit 46 may be implemented using any combination of suitablehardware and/or software to determine this location data. For example,location acquisition unit 46 may be implemented as a global navigationsatellite system (GNSS) receiver configured to determine latitude andlongitude coordinates via GNSS satellite communications using anysuitable GNSS frequency or one or more bands of GNSS frequencies.

Alternatively or additionally, various embodiments of locationacquisition unit 46 are configured to obtain location information viaone or more triangulation and/or network localization techniques. Forexample, location acquisition unit 46 may be configured to utilizewireless communications via communication unit 40 to determine alocation of client device 14 by calculating the location based on signalstrength measurements of one or more base stations, access points, etc.within range of communication unit 40. These base stations and accesspoints could include, for example, cellular base stations, local WANaccess points, etc.

In an embodiment, location acquisition unit 46 is configured todetermine the location data and to send this location data to imagecapture unit 42. In an embodiment, location acquisition unit 46 isconfigured to translate this location data to metadata prior to sendingit to image capture unit 42. The location data could include, forexample, latitude and longitude coordinates, altitude, accuracy data,etc.

Image capture unit 42 is configured to capture an image in a digitalformat. Image capture unit 42 may be implemented as a camera coupled toclient device 14. Although image capture unit 42 is illustrated in FIG.1 as being integrated within client device 14, various embodimentsinclude image capture unit 42 being internal or external to clientdevice 14. For example, image capture unit 42 may be implemented as awebcam coupled to client device 14 and configured to communicate withclient device 14 to transfer digital images. Furthermore, image captureunit 42 may be implemented as a digital camera configured to transferdigital images to client device 14 and/or to quoting engine 12. Suchtransfers may occur via any suitable wired and/or wirelesscommunications, network 16, and/or a transfer from a physical memorycard device (e.g., SD Card, Flash card, etc.), for example.

In an embodiment, image capture unit 42 is configured to use locationdata received from location acquisition unit 46 to add geographicalidentification metadata to a captured image, thereby generating ageotagged image. In an embodiment, image capture unit 42 receives thelocation data as metadata from location acquisition unit 46 and adds itto the captured image to generate a geotagged image. In anotherembodiment, image capture unit 42 translates the location data tometadata to generate a geotagged image.

Communication unit 40 is configured to enable data communicationsbetween client device 14 and quoting engine 12 via network 16. In anembodiment, communication unit 40 is configured to send data and/or oneor more geotagged images captured by image capture unit 42 to quotingengine 12. For example, communication unit 40 may send a geotagged imageof a dwelling to quoting engine 12 via network 16. Further in accordancewith this embodiment, communication unit 40 is configured to receivedata, such as insurance premium quotes, building characteristics, etc.,from quoting engine 12.

As will be appreciated by those of skill in the relevant art(s),communication unit 40 may be implemented with any combination ofsuitable hardware and/or software to enable these functions. Forexample, communication unit 40 may be implemented with any number ofwired and/or wireless transceivers, network interfaces, physical layers(PHY), etc. In embodiments in which client device 14 is a mobile device,communication unit 40 optionally enables communications with one or morenetworks, which may or may not be part of network 16. For example,communication unit 40 could be configured to communicate with cellularand/or WLAN networks in addition to network 16. Networks separate fromnetwork 16 are not shown in FIG. 1 for purposes of brevity.

In various embodiments, communication unit 40 is configured to measurethe strength of signals received from other communication devices withinrange and to provide these measurements to location acquisition unit 46.For example, in embodiments in which client device 14 is implemented asa mobile device, communication unit 40 may be configured to measure thesignal strength of signals received from one or more base stations.Alternatively or additionally, communication unit 40 may be configuredto measure signal strengths of signals received from one or more accesspoints. In this way, communication unit 40 may provide locationacquisition unit 46 an additional or alternate way of determininglocation data. Such embodiments might be particularly useful when, forexample, a GNSS satellite signal is unavailable.

User interface 36 is configured to allow a user to interact with clientdevice 14. For example, user interface 36 may include a user-inputdevice such as an interactive portion of display 38 (e.g., a “soft”keyboard displayed on display 38), an external hardware keyboardconfigured to communicate with client device 14 via a wired or awireless connection (e.g., a Bluetooth keyboard), an external mouse, orany other suitable user-input device.

CPU 32 and/or GPU 34 are configured to communicate with memory 44 tostore to and read data from memory 44. In accordance with variousembodiments, memory 44 is a computer-readable non-transitory storagedevice that may include any combination of volatile (e.g., a randomaccess memory (RAM), or a non-volatile memory (e.g., battery-backed RAM,FLASH, etc.). Memory 44 is configured to store instructions executableon CPU 32 and/or GPU 34. These instructions may include machine readableinstructions that, when executed by CPU 32 and/or GPU 34, cause CPU 32and/or GPU 34 to perform various acts.

Quote application module 50 is a portion of memory 44 configured tostore instructions, that when executed by CPU 32 and/or GPU 34, causeCPU 32 and/or GPU 34 to enable user interface 36 to collect user inputand to display feedback to a user in accordance with one or moreapplications and/or programs. For example, executable instructionsstored in quote application module 50 may enable user interface 36 todisplay one or more prompts to a user and/or to accept user input, whichcould include entering data into one or more data fields, for example.In an embodiment, instructions stored in quoting module 50 enable a userto enter suitable data to obtain one or more insurance premium quotes.

In various embodiments, quote application module 50 enables userinterface 36 to facilitate sending this data to another device, such asquoting engine 12, for example, via communication unit 40. For example,quote application module 50 could include instructions that enable userinterface 36 to collect relevant data from a user and then allow theuser to submit the relevant data to another quoting engine 12 byclicking or pressing an appropriate interactive button. Examples ofrelevant data for homeowners insurance quotes could include personalinformation, contact information, a street address, one or more buildingcharacteristics, and/or a captured geotagged image, etc. Further inaccordance with various embodiments, quote application module 50includes instructions to enable user interface 36 to fill one or moreappropriate fields within a quoting application based on data receivedfrom another device via communication unit 40, such as quoting engine12, for example. Quote application module 50 optionally providesinstructions to enable user interface 36 to prompt a user to verify anyrelevant data entered based on feedback received from anothercommunication device, such as quoting engine 12, for example.

Although FIG. 1 illustrates client device 14 communicating with onlyquoting engine 12, various embodiments include client device 14communicating with any suitable number of other communication devices.Quoting engine 12 includes CPU 18, communication unit 19, and memory 20.

Quoting engine 12 may be implemented as any suitable computing device.In various embodiments, quoting engine 12 is implemented within aserver, a laptop computer, a tablet computer, a smartphone, etc. Invarious embodiments, quoting engine 12 is implemented as an integralpart of client device 14, separate from client device 14, or external toclient device 14. In accordance with embodiments in which quoting engine12 is implemented as an integral part of client device 14, CPU 32 maycommunicate with quoting engine 12, third-party database 30, and/orinsurer database 31 directly via a communication unit, and thus network16 may be omitted. Further in accordance with such an embodiment, CPU 32and/or memory 44 may have a structure similar to, and provide the samefunctionality as, CPU 18 and/or memory 20, respectively. Still furtherin accordance with such an embodiment, one of CPU 18 or CPU 32 may beomitted, and likewise one of memory 20 or memory 44 may be omitted. Whenone of these CPUs or memories are omitted, the functionality of both CPU32 and CPU 18 is integrated into a single CPU, and likewise memory 44and memory 20 may be integrated as part of a single memory device.

Communication unit 19 has a structure substantially similar tocommunication unit 40 and provides substantially the same functionalityas communication unit 40; therefore, only differences betweencommunication unit 40 and communication unit 19 will be furtherdescribed. In various embodiments, communication unit 19 is configuredto enable data communications between client device 14 and quotingengine 12 via network 16. This data could include any suitable relevantquoting data, for example, sent from client device 14 to obtain one ormore homeowners insurance premium quotes. To provide another example,this data could also include data retrieved from third party database 30and/or insurer database 31 and/or calculated insurance premium quotessent from quoting engine 12 to client device 14. Further in accordancewith these embodiments, communication unit 19 is configured tocommunicate with third-party database 30 and/or insurer database 31 toenable CPU 18 to store to and read data from third-party database 30and/or insurer database 31.

CPU 18 is configured to communicate with memory 20 to store to and readdata from memory 20. In accordance with various embodiments, memory 20is a computer-readable non-transitory storage device that may includeany combination of volatile (e.g., a random access memory (RAM), ornon-volatile memory (e.g., battery-backed RAM, FLASH, etc.). Memory 20is configured to store instructions executable by CPU 18. Theseinstructions may include machine readable instructions that, whenexecuted by CPU 18, cause CPU 18 to perform various acts.

Data read/write module 22, quote assessment module 21, and addressverification module 24 are portions of memory 20 configured to storeinstructions executable by CPU 18. Location correlation module 26 andimage recognition module 28 are portions of memory 20 on which addressverification module 24 operates.

Quote assessment module 21 includes instructions that, when executed byCPU 18, causes CPU 18 to perform one or more premium quote calculationsbased on any suitable relevant data. These calculations could be basedon, for example, a risk assessment algorithm that utilizes relevantquoting data such as a dwelling address and/or building characteristicsof a dwelling to generate an insurance premium quote. As will beappreciated by those of skill in the relevant art(s), a quotecalculating algorithm may be tailored based on a particular set of dataand/or assessed risk. For example, if a user's personal data indicatesthat a client is a new customer or a loyal one, then the algorithm maycalculate the insurance premium quote by taking these factors intoconsideration.

Data read/write module 22 includes instructions that, when executed byCPU 18, causes CPU 18 to read data from and/or to write data to thirdparty database 30 and/or insurer database 31 via communication unit 19.In an embodiment, data read/write module 22 enables CPU 18 to accessthird party database 30 and/or insurer database 31 to verify relevantdata received from client device 14. In accordance with anotherembodiment, data read/write module 22 enables CPU 18 to update and/oroverwrite data in third party database 30 and/or insurer database 31.For example, updating may be performed when inconsistent data is foundbetween third party database 30 and insurer database 31. To provideanother example, updating may be performed when data entered by a userand received from client device 14 is inconsistent with data found inthird party database 30 and/or insurer database 31. In an embodiment,data read/write module 22 enables CPU 18 to query data from third partydatabase 30 and/or insurer database 31 and/or store this data in memory20. Further in accordance with this embodiment, data read/write module22 includes instructions that enable CPU 18 to access stored data frommemory 20 when executing instructions from quote assessment module 21,location correlation module 26, and/or image recognition module 28.

Address verification module 24 optionally includes a locationcorrelation module 26 that, when executed by CPU 18, causes CPU 18 toreverse geocode the geotagged location data within an image. In anembodiment, reverse geocoding includes correlating the geotaggedlocation data to location data stored in third party database 30 and/orinsurer database 31. For example, third party database 30 and/or insurerdatabase 31 could include a range of latitude and longitude coordinatesmapped to boundaries of a street address. Using this example, reversegeocoding could include determining whether the geotagged location datafalls within this range of latitude and longitude coordinates. If itdoes, then the instructions stored in address verification module 24could enable CPU 18 to verify that the reverse geocoded address is theaddress of the dwelling for which an insurance premium quote is sought.

Third party database 30 may store any suitable data relevant forcalculation of a homeowners insurance premium quote. Examples of datastored in third party database 30 may include, for example, images ofone or more dwellings, one or more addresses of one or more dwellings, arange of latitude and longitude coordinates associated with one or moredwelling addresses, building characteristics, and/or public record data.To provide further examples, third party database 30 may include claimdata, multiple listing service (MLS) data, property tax records, etc. Invarious embodiments, third party database 30 is implemented withinclient device 14 or quoting engine 12, separate from client device 14 orquery engine 12, or external to client device 14 or query engine 12.

Insurer database 31 may likewise store any suitable data relevant forcalculation of a homeowners insurance premium quote. Examples of datastored in insurer database 30 may include, for example, images of one ormore dwellings, one or more addresses of one or more dwellings, a rangeof latitude and longitude coordinates associated with one or moredwelling addresses, building characteristics, previous homeownersinsurance information on file, current and/or previous homeownerspremium quotes, etc. In various embodiments, insurer database 30includes any combination of publicly available data and/or private dataheld by an insurer that is not publicly available. For example, aninsurer database dwelling entry could include a dwelling address, arange of latitude and longitude coordinates associated with the propertyboundaries of the dwelling address, and one or more images of thedwelling address. In various embodiments, insurer database 31 isimplemented within client device 14 or quoting engine 12, separate fromclient device 14 or query engine 12, or external to client device 14 orquery engine 12.

Address verification module 24 optionally includes an image recognitionmodule 28. Image recognition module 28 includes instructions that, whenexecuted by CPU 18, causes CPU 18 to correlate the geotagged imagereceived from client device 14 with one more images stored in thirdparty database 30 and/or insurer database 31. Image recognition 28 mayinclude any image recognition algorithm to enable CPU 18 to performimage correlation. For example, image recognition module 28 couldinclude instructions for an edge matching algorithm, a histogrammatching algorithm, a grayscale matching algorithm, etc.

In various embodiments, address verification module 24 includes onlylocation correlation module 26, only image recognition module 28, orboth location correlation module 26 and image recognition module 28.Embodiments of address verification module 24 including both locationcorrelation module 26 and image recognition module 28 may beimplemented, for example, when additional verification is desired toensure that a received geotagged image is correlated to both an addressand an image in third party database 30 and/or insurer database 31.

In accordance with various embodiments, any of quote assessment module21, data read/write module 22, address verification module 24, locationcorrelation module 26, and/or image recognition module 28 operates as aseparately executable software application, a plugin that extends thefunctionality of another software application such as a web browser, anapplication programming interface (API) invokable by a softwareapplication, etc. The instructions included within any of quoteassessment module 21, data read/write module 22, address verificationmodule 24, location correlation module 26, and/or image recognitionmodule 28 may be compiled and executable on the CPU 18 directly, or notcompiled and interpreted by the CPU 18 on a runtime basis.

FIG. 1 illustrates quoting engine 12 coupled directly to third partydatabase 30 and insurer database 31 for purposes of brevity. As will beappreciated by those of skill in the relevant art(s), variousembodiments of quoting engine 12 include accessing third party database30 and/or insurer database 31 via any suitable network, which may besubstantially similar to network 16, for example. In accordance withsuch embodiments, quoting engine 12 is configured to access third partydatabase 30 and insurer database 31 via a network such that third partydatabase 30, insurer database 31, and/or quoting engine 12 need not beco-located. For example, in accordance with such embodiments, quotingengine 12 may access third party database 30 via a connection to theInternet to download relevant premium quoting information. To provideanother example, quoting engine 12 may access insurer database 31 via alocal, secure connection to one or more private servers to downloadrelevant premium quoting information.

Although illustrated as a single engine in FIG. 1, in variousembodiments, quoting engine 12 may consist of any number or group of oneor more quoting engines. In accordance with such embodiments, eachquoting engine may include one or more CPUs and be configured to operateindependently of the other quoting engines. Quoting engines operating asa group may process requests from client device 14 individually (e.g.,based on their availability) and/or concurrently (e.g., parallelprocessing). Quoting engines operating as a group may process requestsfrom the client device 14 in a prioritized and/or distributed manner.For example, an operation associated with processing a request may beperformed on one quoting engine while another operation associated withprocessing the same request (or a different request) is performed onanother quoting engine.

FIG. 2 illustrates a quote method 200 in accordance with an exemplaryembodiment of the present disclosure. In various embodiment, quotemethod 200 is implemented as a part of quote system 10, as shown in FIG.1.

Method 200 begins at block 202, at which a quick quote application isstarted on a first device. This first device could include, for example,client device 14, as shown in FIG. 1. Further in accordance with thisembodiment, this application could include, for example, an applicationrun by CPU 32 executing instructions stored in quote application module50.

At block 204, an image is taken of a dwelling including geotaggedinformation and sent to a second device. This image could be taken, forexample, by a user of the first device. The image could include, forexample, a dwelling for which a user wishes to obtain a homeownersinsurance quote. The second device could include, for example, quotingengine 12, as shown in FIG. 1.

At block 206, the geotagged information in the geotagged image isreverse geocoded to determine a reverse geocoded address. For example,this determination could be made at quoting engine 12 or at clientdevice 14 by accessing third party database 30 and/or insurer database31.

At block 208, the reverse geocoded address is sent back to the firstdevice. This could include, for example, sending the reverse geocodedaddress from quoting engine 12 back to client device 14 via network 16.

At block 210, a determination is made whether the reverse geocodedaddress has been verified as being correct. In an embodiment, thisverification includes a user determining whether the reverse geocodedaddress matches the address of the dwelling that was captured in thegeotagged image. This determination could be made, for example, bydisplaying the reverse geocoded address to the user and prompting theuser to verify the reverse geocoded address is correct. If the userdetermines that the reverse geocoded address is correct, then method 200continues to block 214. If the user determines that the reverse geocodedaddress is incorrect, then method 200 continues to block 212.

In another embodiment, the reverse geocoded address is verified withoutuser intervention. For example, the reverse geocoded addresses obtainedfrom third party database 30 could be compared to the reverse geocodedaddress obtained from insurer database 31. For example, a reversegeocoded address ‘A’ obtained from third party database 30 might notmatch a reverse geocoded address ‘B’ obtained from insurer database 31.In accordance with such an embodiment, method 200 continues to block 212when mismatched and/or inconsistent reverse geocoded addresses areidentified. If the reverse geocoded addresses match, then method 200continues to block 214.

At block 212, an incorrect, mismatched, and/or inconsistent reversegeocoded address is reconciled. In an embodiment, reconciling thereverse geocoded address is performed in response to an updated dwellingaddress verified by a user in block 210. In accordance with such anembodiment, reconciling the reverse geocoded address could include, forexample, quoting engine 12 updating third party database 30 and/orinsurer database 31 with the updated dwelling address sent from clientdevice 14 to quoting engine 12.

In another embodiment, reconciling the reverse geocoded address isperformed by identifying mismatches between reverse geocoded addressesobtained from third party database 30 and insurer database 31. Inaccordance with such an embodiment, a priority hierarchy may be utilizedto resolve inconsistencies. For example, an insurer may decide that onedatabase contains more reliable data than the other database. Therefore,in an embodiment, instructions stored in location correlation module 26and/or quote assessment module 21 resolve such inconsistencies based ona preferred database.

Further in accordance with this embodiment, reconciling reverse geocodedaddress could include quoting engine 12 updating third party database 30or insurer database 31 based on which database is more accurate, suchthat both databases contain the same address data for future use. Aswill be appreciated by those of skill in the relevant art(s), thedecision of which database is deemed more accurate may be decided basedon user knowledge, preferences, an inability to update one or moreportions of third party database 30 and/or insurer database 31, etc.

In an embodiment, no address verification is performed. In accordancewith such an embodiment, a reverse geocoded address obtained from eitherthird party database 30 or insurer database 31 is assumed to be correct,and thus blocks 208, 210, and 212 are omitted. This embodiment isillustrated by the dashed line in FIG. 2 indicating a flow of method 200from block 206 to block 214.

At block 214, an insurance premium quote is determined based on theverified dwelling address, and this premium quote is sent back to thefirst device. This determination could be made, for example, by one ormore algorithms performed by CPU 18 executing instructions stored inquote assessment module 21. If the reverse geocoded address wasreconciled at block 212, then the premium quote determined at block 214is based on the updated/reconciled address in block 212.

At block 216, a determination is made whether other dwellings in thevicinity match the insurance premium quote calculated in block 214, andthese results are sent back to the first device. This determinationcould be made, for example, by one or more algorithms performed by CPU18 executing instructions stored in quote assessment module 21. Theseinstructions could include, for example, an algorithm that uses a targetpercentage of the premium quote determined in block 214 and/or a radiusfrom the verified dwelling address used for the calculation in block214. For example, using a premium quote of $100 per month for dwellingaddress ‘A’ as an example, quoting engine 12 may access third partydatabase 30 and/or insurer database 31 to look up other dwellings withina mile radius of address A that have premium quotes within ±10% of thecalculated quoted premium (i.e., $90-$110 per month).

In an embodiment, the target percentage and/or dwelling radius valuesare predetermined. In another embodiment, the target percentage and/ordwelling radius values are chosen by a user of client device 14.Embodiments including block 216 may be particularly useful when, forexample, a potential homeowner is looking for insurance quotes for aproperty that has not yet been purchased and other dwelling premiums inthe area may be of interest to the user. In some embodiments, a user mayhave already obtained several quotes using any suitable methods asdiscussed throughout this disclosure. In accordance with suchembodiments, block 216 could include quoting engine 12 accessing thirdparty database 30 and/or insurer database 31 to retrieve quotes thatmatch the target percentage and/or dwelling radius values based on auser's prior quoting history.

In addition, in various embodiments, block 216 could include a userobtaining several quotes using any suitable methods as discussedthroughout this disclosure, which are then stored in a database, such asinsurer database 31, for example. Further in accordance with suchembodiments, block 216 could include quoting engine 12 accessing insurerdatabase 31 to obtain those quotes for each of the properties that matchthe target percentage and/or dwelling radius values. In other words,such embodiments allow the various quoting systems as described hereinto be applied to several dwellings within a dwelling radius, with only asubset of those dwellings that match the target percentage within thedwelling radius being shown to the user.

In other embodiments, block 216 could include quoting engine 12accessing third party database 30 and/or insurer database 31 to retrievequotes that match the target percentage and/or dwelling radius valuesbased on any suitable quoting system. Such quotes could include, forexample, premiums that may or may not have been previously quoted inaccordance with methods as discussed throughout this disclosure. Inaccordance with an embodiment, block 216 is omitted.

FIG. 3 illustrates a quote method 300 in accordance with an exemplaryembodiment of the present disclosure. In various embodiments, detailedquote method 300 is implemented as a part of quote system 10, as shownin FIG. 1. In an embodiment, quote method 300 provides a more preciseinsurance premium quote compared to quote method 200.

Method 300 begins at block 302, at which a detailed quote application isstarted on a first device. This first device could include, for example,client device 14, as shown in FIG. 1. Further in accordance with thisembodiment, this application could include, for example, an applicationrun by CPU 32 executing instructions stored in quote application module50.

At block 304, a user enters personal information and/or an address ofthe dwelling for which a detailed homeowners insurance premium quote issought. Personal information could include, for example, contactinformation such as the users' name, e-mail address, etc. In accordancewith an embodiment, the dwelling address is entered by the user. Inaccordance with other embodiments, the dwelling address is not enteredby the user.

At block 306, a determination is made whether a previous quoteapplication been completed, such as quote method 200, for example. Forexample, a user may initially run quote method 200 from client device 14to determine an insurance premium quote based on only a geotaggedcaptured image. Using this example, a user may later launch quote method300 to obtain a more accurate quote based on additional information. Inaccordance with an embodiment, client 14 stores the previously capturedgeotagged image and/or quoted premium in memory 44. In such a case, thegeotagged image does not need to be retaken, and therefore method 300continues to block 308. However, if quote method 200 has not beencompleted and/or a geotagged image of the dwelling does not yet exist,then method 300 continues to block 318.

At block 318, an image is taken of a dwelling including geotaggedinformation. This image could be taken, for example, by a user of theclient device. The image could include, for example, a dwelling forwhich a user wishes to obtain a homeowners insurance premium quote.

At block 308, a reverse geocoded address is determined using thegeotagged data within the image that was either already captured duringquote method 200 or at block 318. In an embodiment in which no addresshas been entered at block 304, block 308 operates in substantially thesame manner as blocks 206, 208, 210, and 212, as shown in FIG. 2. But inaccordance with an embodiment in which a user has entered a dwellingaddress, block 308 additionally includes verifying the reverse geocodedaddress using the dwelling address. This verification could beperformed, for example, by CPU 18 executing instructions stored inlocation correlation module 26. This verification could include, forexample, CPU 18 verifying whether a reverse geocoded address obtainedfrom third party database 30 and/or insurer database 31 matches thedwelling address entered by the user. If the dwelling address matchesthe reverse geocoded address obtained from third party database 30and/or insurer database 31, then method 300 continues to block 310.

However, if the reverse geocoded address obtained from third partydatabase 30 and/or insurer database 31 does not match the dwellingaddress entered by the user, then block 308 additionally includesreconciling this inconsistency. For example, similar to block 210 asshown in FIG. 2, reconciling could include generating a prompt for theuser to verify and potentially correct the entered address. To provideanother example, reconciling could include updating third party database30 and/or insurer database 31 with the dwelling address entered by theuser. As previously discussed with regards to block 212 in FIG. 2,various embodiments of block 308 include reconciling via hierarchicalprioritization of a preferred source of a dwelling address. Inaccordance with such embodiments, either the reverse geocoded address orthe dwelling address entered by a user is selected based on any numberof preferences.

For example, in an embodiment, reconciling including updating an addressstored in third party database 30 and/or insurer database 31 with adwelling address entered by a user. In another embodiment, the reversegeocoded address determined from either third party database 30 orinsurer database 31 overrides the dwelling address entered by a user.

In accordance with various embodiments, reconciling optionally includesflagging these inconsistencies between a dwelling address entered by auser and addresses found in either third party database 30 or insurerdatabase 31. Further in accordance with such embodiments, reconcilingincludes generating a notification (e.g., an e-mail) to one or moreinsurance agents to follow up and rectify any inconsistencies.

At block 310, the image of the dwelling is verified using an image ofthe dwelling corresponding to the reverse geocoded address. This imagecould include, for example, an image stored in third party database 30and/or insurer database 31. In an embodiment, block 310 includesreconciling for inconsistencies between these images by updating thethird party database 30 and/or insurer database 31 or by adding thecaptured dwelling image if no image is present in either database. Inanother embodiment, verifying the captured image includes determiningthat the dwelling image and the image stored in third party database 30and/or insurer database 31 match one another. This could include, forexample, using any suitable image recognition algorithm executed by CPU18 reading instructions from image recognition module 28.

Similar to the address reconciliation embodiments described with respectto block 308, various embodiments of reconciling the dwelling imageinclude prioritizing and reconciling images found in third partydatabase 30 and/or insurer database 31 with the captured image. Forexample, reconciling the image could include sending the image back to auser to verify the image. To provide another example, reconciling theimage could include reconciling mismatches between different imagesfound in third party database 30 and/or insurer database 31 by updatingone (or both) of these databases so they contain the same image.

At block 312, method 300 includes determining relevant information forthe calculation of a detailed insurance premium quote. This relevantinformation could include, for example, building characteristics, asurrounding area of the dwelling, dwelling construction materials, theage of the dwelling, etc. In accordance with various embodiments, dataentries corresponding to the reverse geocoded address in third partydatabase 30 and/or insurer database 31 include this relevantinformation. In accordance with such embodiments, this information isobtained from third party database 30 and/or insurer database 31. Thisinformation could be obtained, for example, by CPU 18 executinginstructions stored in data read/write module 22. In an embodiment,quoting engine 12 retrieves the relevant information and optionallysends it back to client device 14, where this relevant information isentered into appropriate fields of the detailed quoting applicationwithin user interface 36. Further in accordance with this embodiment, auser does not need to manually enter this information.

At block 314, method 300 includes verifying the relevant informationobtained in block 312. In an embodiment in which quoting engine 12 sendsthis information back to client device 14, block 314 could include, forexample, prompting a user to consider this information and to verifythat it is correct. Reconciliation in block 314 could include, forexample, reconciling inconsistencies between information indicated asincorrect by the user, information obtained via third party database 30,and/or information obtained via insurer database 31.

That is, if a user determines that there is an inconsistency and/orthird party database 30 and/or insurer database 31 contain inconsistentinformation, reconciling in block 314 could include reconciling thisinformation in accordance with an established priority, as previouslydiscussed with respect to blocks 308 and 310. Therefore, variousembodiments of block 314 include user verification of the relevantinformation, comparison of the relevant information from third partydatabase 30 and/or insurer database 31, and reconciliation/updating ofthe relevant information between the user, third party database 30,and/or insurer database 31.

At block 316, a detailed insurance premium is determined based on theverified dwelling address and the verified relevant quoting information.This determination could be made, for example, by one or more algorithmsperformed by CPU 18 utilizing instructions stored in quote assessmentmodule 21. This algorithm could be based on, for example, one or morerisk assessment calculations associated with the dwelling address and/orthe relevant quoting information. If the dwelling address, dwellingimage, and/or relevant information was reconciled at blocks 308, 310,and 314, respectively, then this determination is based on theupdated/reconciled dwelling address, dwelling image, and/or relevantinformation.

In an embodiment of method 300, no user intervention is required afterblocks 304 and/or 318. For example, once a user enters personalinformation, captures an image of the dwelling with geocodedinformation, and/or enters an address of the dwelling, the insurancepremium quote could be displayed to the user via user interface 36. Inaccordance with such an embodiment, the personal information, capturedgeocoded image, and/or address of the dwelling are sent to quotingengine 12 once the user decides to submit this information. Inaccordance with such an embodiment, the insurance premium quote isdisplayed for the user after this information is submitted, and a useris not prompted to reconcile or verify any information.

Further in accordance with such an embodiment, the user may optionallybe notified of any conflicts that require reconciliation with thereturned quoted premium. The user may then be prompted to verify and/orreconcile any data used in calculating the quoted premium and tore-submit this data for another quote. In this way, method 300 allows auser to obtain an initial detailed and accurate quote quickly that maynot require any data reconciliation while providing feedback to the useronce the quote is generated in case reconciliation is needed.

The following additional considerations apply to the foregoingdiscussion. Throughout this specification, plural instances mayimplement components, operations, or structures described as a singleinstance. Although individual operations of one or more methods areillustrated and described as separate operations, one or more of theindividual operations may be performed concurrently, and nothingrequires that the operations be performed in the order illustrated.Structures and functionality presented as separate components in exampleconfigurations may be implemented as a combined structure or component.Similarly, structures and functionality presented as a single componentmay be implemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter of the present disclosure.

Additionally, certain embodiments are described herein as includinglogic or a number of components or modules. Modules may constituteeither software modules (e.g., code stored on a machine-readable medium)or hardware modules. A hardware module is tangible unit capable ofperforming certain operations and may be configured or arranged in acertain manner. In example embodiments, one or more computer systems(e.g., a standalone, client or server computer system) or one or morehardware modules of a computer system (e.g., a processor or a group ofprocessors) may be configured by software (e.g., an application orapplication portion) as a hardware module that operates to performcertain operations as described herein.

In some cases, a hardware module may include dedicated circuitry orlogic that is permanently configured (e.g., as a special-purposeprocessor, such as a field programmable gate array (FPGA) or anapplication-specific integrated circuit (ASIC)) to perform certainoperations. A hardware module may also include programmable logic orcircuitry (e.g., as encompassed within a general-purpose processor orother programmable processor) that is temporarily configured by softwareto perform certain operations. It will be appreciated that the decisionto implement a hardware module in dedicated and permanently configuredcircuitry or in temporarily configured circuitry (e.g., configured bysoftware) may be driven by cost and time considerations.

Accordingly, the term hardware should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering embodiments in which hardwaremodules are temporarily configured (e.g., programmed), each of thehardware modules need not be configured or instantiated at any oneinstance in time. For example, where the hardware modules comprise ageneral-purpose processor configured using software, the general-purposeprocessor may be configured as respective different hardware modules atdifferent times. Software may accordingly configure a processor, forexample, to constitute a particular hardware module at one instance oftime and to constitute a different hardware module at a differentinstance of time.

Hardware and software modules can provide information to, and receiveinformation from, other hardware and/or software modules. Accordingly,the described hardware modules may be regarded as being communicativelycoupled. Where multiple of such hardware or software modules existcontemporaneously, communications may be achieved through signaltransmission (e.g., over appropriate circuits and buses) that connectthe hardware or software modules. In embodiments in which multiplehardware modules or software are configured or instantiated at differenttimes, communications between such hardware or software modules may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware or software moduleshave access. For example, one hardware or software module may perform anoperation and store the output of that operation in a memory device towhich it is communicatively coupled. A further hardware or softwaremodule may then, at a later time, access the memory device to retrieveand process the stored output. Hardware and software modules may alsoinitiate communications with input or output devices, and can operate ona resource (e.g., a collection of information).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods or routines described herein may be at leastpartially processor-implemented. For example, at least some of theoperations of a method may be performed by one or processors orprocessor-implemented hardware modules. The performance of certain ofthe operations may be distributed among the one or more processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The one or more processors may also operate to support performance ofthe relevant operations in a “cloud computing” environment or as a SaaS.For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., application program interfaces(APIs).)

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

Some portions of this specification are presented in terms of algorithmsor symbolic representations of operations on data stored as bits orbinary digital signals within a machine memory (e.g., a computermemory). These algorithms or symbolic representations are examples oftechniques used by those of ordinary skill in the data processing artsto convey the substance of their work to others skilled in the art. Asused herein, an “algorithm” or a “routine” is a self-consistent sequenceof operations or similar processing leading to a desired result. In thiscontext, algorithms, routines and operations involve physicalmanipulation of physical quantities. Typically, but not necessarily,such quantities may take the form of electrical, magnetic, or opticalsignals capable of being stored, accessed, transferred, combined,compared, or otherwise manipulated by a machine. It is convenient attimes, principally for reasons of common usage, to refer to such signalsusing words such as “data,” “content,” “bits,” “values,” “elements,”“symbols,” “characters,” “terms,” “numbers,” “numerals,” or the like.These words, however, are merely convenient labels and are to beassociated with appropriate physical quantities.

Unless specifically stated otherwise, discussions herein using wordssuch as “processing,” “computing,” “calculating,” “determining,”“presenting,” “displaying,” or the like may refer to actions orprocesses of a machine (e.g., a computer) that manipulates or transformsdata represented as physical (e.g., electronic, magnetic, or optical)quantities within one or more memories (e.g., volatile memory,non-volatile memory, or a combination thereof), registers, or othermachine components that receive, store, transmit, or displayinformation.

As used herein any reference to “one embodiment” or “an embodiment”means that a particular element, feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment. The appearances of the phrase “in one embodiment” in variousplaces in the specification are not necessarily all referring to thesame embodiment.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. For example, some embodimentsmay be described using the term “coupled” to indicate that two or moreelements are in direct physical or electrical contact. The term“coupled,” however, may also mean that two or more elements are not indirect contact with each other, but yet still co-operate or interactwith each other. The embodiments are not limited in this context.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,method, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such process, method,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive or and not to an exclusive or. For example,condition A or B is satisfied by any one of the following: A is true (orpresent) and B is false (or not present), A is false (or not present)and B is true (or present), and both A and B are true (or present).

In addition, use of the “a” or “an” are employed to describe elementsand components of the embodiments herein. This is done merely forconvenience and to give a general sense of the description. Thisdescription should be read to include one or at least one and thesingular also includes the plural unless it is obvious that it is meantotherwise.

Upon reading this disclosure, those of skill in the art will appreciatestill additional alternative structural and functional designs forproviding an interface for inspecting indoor and outdoor map datathrough the disclosed principles herein. Thus, while particularembodiments and applications have been illustrated and described, it isto be understood that the disclosed embodiments are not limited to theprecise construction and components disclosed herein. Variousmodifications, changes and variations, which will be apparent to thoseskilled in the art, may be made in the arrangement, operation anddetails of the method and apparatus disclosed herein without departingfrom the spirit and scope defined in the appended claims.

What is claimed is:
 1. A computer-implemented method for determining aninsurance premium quote, comprising: storing, via one or moreprocessors, a first image of a dwelling including geotagged informationthat is indicative of a geographic location where the first image of thedwelling was captured; correlating, via one or more processors, thegeotagged information to geographic location data stored in a firstdatabase to identify a reverse geocoded address; updating, via one ormore processors, the first database when the geotagged information iscorrelated with the geographic location data; executing, via one or moreprocessors, an image matching recognition algorithm to match the firstimage of the dwelling to a second image of the dwelling that is storedin a second database that correlates the second image of the dwelling toa database dwelling address and one or more building characteristics,wherein the image matching recognition algorithm includes one or more ofan edge matching algorithm, a histogram matching algorithm, and agrayscale matching algorithm; when the reverse geocoded addressesmatches the database dwelling address: identifying, via one or moreprocessors, the correct dwelling address as being the same as thereverse geocoded addresses and the database dwelling address; when thereverse geocoded addresses does not match the database dwelling address:identifying, via one or more processors, the correct dwelling address aseither the reverse geocoded address or the database dwelling address byapplying a pre-established set of hierarchical prioritization that isbased upon data source reliability that identifies one of the first orthe second database as being the more reliable database, wherein thefirst database is identified as being more reliable than the seconddatabase when the first database is updated; calculating, via one ormore processors, an insurance premium quote using the correct dwellingaddress and one or more building characteristics stored in one of thefirst or the second database that is associated with the correctdwelling address; displaying, via one or more processors, the insurancepremium quote; transmitting, by one or more processors, the one or morebuilding characteristics to a computing device; and populating, by thecomputing device, one or more building characteristic fields within acomputer-implemented application executed on the computing device withthe one or more respective building characteristics.
 2. Thecomputer-implemented method of claim 1, further comprising: identifying,via one or more processors, a plurality of other dwellings within athreshold distance of the correct dwelling address that have insurancepremium quotes matching the insurance premium quote within a thresholdpremium amount; and displaying, via one or more processors, an insurancepremium quote for each respective one of the plurality of otherdwellings.
 3. The computer-implemented of claim 1, further comprising:when the reverse geocoded addresses does not match the database dwellingaddress: updating, via one or more processors, one of the first or thesecond database that is associated with an incorrect dwelling addressbased upon the hierarchical prioritization.
 4. The computer-implementedmethod of claim 1, further comprising: prompting, via one or moreprocessors, a user to determine whether the reverse geocoded addressmatches the database dwelling address, and determining whether thereverse geocoded address matches the database dwelling address basedupon the user's response to the prompt.
 5. The computer-implementedmethod of claim 1, wherein: the first database is implemented as aninsurer database, the second database is implemented as a third-partydatabase, and the hierarchical prioritization identifies the insurerdatabase as the more reliable database such that the correct dwellingaddress is identified as the reverse geocoded address when the reversegeocoded addresses does not match the database dwelling address.
 6. Anon-transitory, tangible computer-readable medium storing machinereadable instructions that, when executed by a processor, cause theprocessor to: store a first image of a dwelling including geotaggedinformation that is indicative of a geographic location where the firstimage of the dwelling was captured; correlate the geotagged informationto geographic location data stored in a first database to identify areverse geocoded address; update, via one or more processors, the firstdatabase when the geotagged information is correlated with thegeographic location data; perform an image matching recognitionalgorithm to match the first image of the dwelling to a second image ofthe dwelling that is stored in a second database that correlates thesecond image of the dwelling to a database dwelling address and one ormore building characteristics, wherein the image matching recognitionalgorithm includes one or more of an edge matching algorithm, ahistogram matching algorithm, and a grayscale matching algorithm; whenthe reverse geocoded addresses matches the database dwelling address:identify the correct dwelling address as being the same as the reversegeocoded addresses and the database dwelling address; when the reversegeocoded addresses does not match the database dwelling address:identify the correct dwelling address as either the reverse geocodedaddress or the database dwelling address by applying a pre-establishedset of hierarchical prioritization that is based upon data sourcereliability that identifies one of the first or the second database asbeing the more reliable database, wherein the first database isidentified as being more reliable than the second database when thefirst database is updated; calculate an insurance premium quote usingthe correct dwelling address and one or more building characteristicsstored in one of the first or the second database that is associatedwith the correct dwelling address; transmit the insurance premium quotesuch that, upon being received by a computing device, the insurancepremium quote is displayed on the computing device; and transmit the oneor more building characteristics to a computing device such that, uponbeing received by a computing device, the one or more buildingcharacteristic fields are populated with the one or more respectivebuilding characteristics within a computer-implemented applicationexecuted on the computing device.
 7. The non-transitory, tangiblecomputer-readable medium of claim 6, further storing instructions that,when executed by the processor, cause the processor to: identify aplurality of other dwellings within a threshold distance of the correctdwelling address that have insurance premium quotes matching theinsurance premium quote within a threshold premium amount; and transmitan insurance premium quote for each of the plurality of other dwellingssuch that, upon being received by the computing device, the insurancepremium quote for each of the plurality of other dwellings is displayedon the computing device.
 8. The non-transitory, tangiblecomputer-readable medium of claim 6, further storing instructions that,when executed by the processor, cause the processor to: when the reversegeocoded addresses does not match the database dwelling address, toupdate one of the first or the second database that is associated withan incorrect dwelling address based upon the hierarchicalprioritization.
 9. The non-transitory, tangible computer-readable mediumof claim 6, further storing instructions that, when executed by theprocessor, cause the processor to: receiving a response from a userindicating whether the reverse geocoded address matches the databasedwelling address, and determining whether the reverse geocoded addressmatches the database dwelling address based upon the user's response.10. The non-transitory, tangible computer-readable medium of claim 6,wherein: the first database is implemented as an insurer database, thesecond database is implemented as a third-party database, and theinstructions to identify the correct dwelling address as either thereverse geocoded address or the database dwelling address by applying ahierarchical prioritization include instructions that, when executed bythe processor, cause the processor to: identify the insurer database asthe more reliable database such that the correct dwelling address isidentified as the reverse geocoded address when the reverse geocodedaddresses does not match the database dwelling address.
 11. An insurancepremium quoting system, comprising: a mobile computing device configuredto transmit a first image of a dwelling including geotagged informationthat is indicative of a geographic location where the first image of thedwelling was captured; and a quote engine configured to: correlate thegeotagged information to geographic location data stored in a firstdatabase to identify a reverse geocoded address; update, via one or moreprocessors, the first database when the geotagged information iscorrelated with the geographic location data; execute an image matchingrecognition algorithm to match the first image of the dwelling to asecond image of the dwelling that is stored in a second database thatcorrelates the second image of the dwelling to a database dwellingaddress and one or more building characteristics, wherein the imagematching recognition algorithm includes one or more of an edge matchingalgorithm, a histogram matching algorithm, and a grayscale matchingalgorithm; when the reverse geocoded addresses matches the databasedwelling address: identify the correct dwelling address as being thesame as the reverse geocoded addresses and the database dwellingaddress; when the reverse geocoded addresses does not match the databasedwelling address: identify the correct dwelling address as either thereverse geocoded address or the database dwelling address by applying apre-established set of hierarchical prioritization that is based upondata source reliability that identifies one of the first or the seconddatabase as being the more reliable database, wherein the first databaseis identified as being more reliable than the second database when thefirst database is updated; calculate an insurance premium quote usingthe correct dwelling address and one or more building characteristicsstored in one of the first or the second database that is associatedwith the correct dwelling address; transmit the insurance premium quoteto the mobile computing device, wherein the mobile computing device isfurther configured to display the insurance premium quote; and transmitthe one or more building characteristics to a computing device, whereinthe mobile computing device is further configured to populate one ormore building characteristic fields within a computer-implementedapplication executed on the mobile computing device with the one or morerespective building characteristics.
 12. The insurance premium quotingsystem of claim 11, wherein the quoting engine is further configured toidentify a plurality of other dwellings within a threshold distance ofthe correct dwelling address that have insurance premium quotes matchingthe insurance premium quote within a threshold premium amount, and totransmit an insurance premium quote for each respective one of theplurality of other dwellings to the mobile computing device, and whereinthe mobile computing device is further configured to display eachrespective one of the plurality of other dwellings.
 13. The insurancepremium quoting system of claim 11, wherein the quoting engine isfurther configured to update one of the first or the second databasethat is associated with the incorrect dwelling address based upon thehierarchical prioritization when the reverse geocoded addresses does notmatch the database dwelling address.
 14. The insurance premium quotingsystem of claim 11, wherein: the first database is implemented as aninsurer database, the second database is implemented as a third-partydatabase, and the hierarchical prioritization identifies the insurerdatabase as the more reliable database such that the correct dwellingaddress is identified as the reverse geocoded address when the reversegeocoded addresses does not match the database dwelling address.